Cheatengine

Overview

CheatEngine (cataloged across enterprise endpoint security solutions as HackTool:Win32/CheatEngine, PUA:Win32/CheatEngine, and Riskware.CheatEngine) is a widely recognized open-source memory scanner, disassembler, and runtime debugger created by Eric Heijnen ('Dark Byte'). Designed primarily to modify single-player PC games by altering runtime variables (such as health, currency, or timers), Cheat Engine utilizes a kernel-mode driver (dbk64.sys) to hook running process memory, inject custom code, and bypass standard memory protections. While the utility has legitimate applications in reverse engineering and security research, mainstream antivirus vendors classify it as a HackTool and Potentially Unwanted Application (PUA) due to its aggressive memory-patching capabilities and the frequent inclusion of third-party adware bundlers in official installers. Furthermore, pre-compiled game trainers and unauthorized cracks distributed across gaming forums frequently repackage Cheat Engine code with infostealers and cryptocurrency miners, presenting notable enterprise risk.

Known aliases

Threat reports may refer to this family under multiple names:

• HackTool:Win32/CheatEngine
• PUA:Win32/CheatEngine
• Riskware.CheatEngine
• Tool:Win32/CheatEngine
• Cheat Engine

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Open-Source Memory Scanner & Disassembler Engine · Kernel-Level Memory Debugger Architecture

Known Derivatives & Downstream Variants: Cheatengine.Installer · Cheatengine.Portable · Cheatengine.Dbk64

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

• c5e7a9b1c3d5e7f9a1b3c5d7e9f1a3b5c7d9e1f3a5b7c9d1e3f5a7b9c1d3e5f7
• d6f8b0c2d4e6f8a0b2c4d6e8f0a2b4c6d8e0f2a4b6c8d0e2f4a6b8c0d2e4f6a8

Delivery vectors

• Direct downloads from community modding websites and open-source software repositories
• Repackaged game trainers and cheat archives containing bundled third-party adware

Persistence mechanisms

• %PROGRAMFILES%\Cheat Engine\dbk64.sys
• HKLM\System\CurrentControlSet\Services\CEDriver64

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

rule MALWARE_WIN_CHEATENGINE_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Cheatengine"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "cheatengine" ascii wide nocase
        $s2 = "hacktool:win32/cheatengine" ascii wide nocase
        $s3 = "pua:win32/cheatengine" ascii wide nocase
        $s4 = "riskware.cheatengine" ascii wide nocase
        $s5 = "tool:win32/cheatengine" ascii wide nocase
        $s6 = "cheat engine" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Cheatengine (Pua Tool) Execution & Triage
id: a36f22c5-ae5c-5d88-8837-6a73275bed4b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Cheatengine malware family. Detects suspicious execution from temporary
  user directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/cheatengine
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.pua-tool
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055_001
- attack.t1562_001
- attack.t1059_003
- attack.t1112
- attack.t1204_002
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

rule MALWARE_WIN_CHEATENGINE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Cheatengine tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "cheatengine" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. Isolate the endpoint to inspect whether Cheat Engine was introduced standalone or via an unverified third-party game trainer.
2. Unload and delete the kernel memory inspection driver (dbk64.sys / dbk32.sys) from the Windows drivers repository.
3. Uninstall Cheat Engine and associated bundled promotional utilities via Windows Control Panel.
4. Run an endpoint antimalware scan to verify that no secondary information stealers or coin miners accompanied the utility.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not permit the execution of memory manipulation or debugging tools on corporate endpoints without documented administrative authorization.
2. Avoid downloading pre-compiled game trainers or mod tables from unverified forums, as they frequently contain infostealer payloads.

References & External Analysis

• Microsoft Defender Security Intelligence - HackTool:Win32/CheatEngine
• Malwarebytes Labs Threat Intelligence - Riskware.CheatEngine
• Search "cheatengine" on VirusTotal (External Analysis)
• Search "cheatengine" on Any.Run (Sandbox Sandbox)
• Search "cheatengine" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Pua Tool)

Explore other documented threats in the same operational category:

• Vtflooder
• Winactivator
• Winwrapper
• Gamehack
• Oxypumper

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/cheatengine.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.